Development in Project ArkC has suspended for months due to the following reasons:
- Changes in the political environment in China to suppress the civil society since late 2015 exposed developers to potential personal threats.
- Moves from major Chinese ISPs (provide end users with Internet service behind NAT) limit the application of the project from the technology aspect.
- Other personal concerns of team members
The first reason is most important to the suspension of ArkC. Therefore, developers of ArkC usually refer to “Change in Regulatory Environment” as the reason for suspension.
However, similar as the two ways of expression may seem, they are fundamentally different because the regulations should be bound by law. Certainly Not the political environment in China mainland.
A collection of all open-source code of ArkC is available on a new Github repository: projectarkc/collection.
As you may know, “帝吧出征” happened in the previous months and utilized VPNs to start unpleasant arguments on Facebook pages. To summarize what they (partly) did, they denied the general freedom of speech, with their freedom of speech gained via their VPNs.
ArkC could be used as one of their tools and become merely a (free and effective) tool to deny the freedom of speech. But this is not what we want to see. Rational beings should be self-contradictory.
As to the incidents itself, we believe we ought to help people understand the reasoning behind “Freedom”, “Freedom of speech” and many else. People should not accept “Freedom” because freedom merely makes them feel good —- such kind of freedom is not universal and cannot be extended to the general public. “Freedom” shall be understood as a theory, a proven concept based on moral and political philosophy.
For us, we believe “Freedom of Speech and Freedom to access information without censorship” is essential for the exchange of thought. We ourselves hold diverse political opinions, as netizens often do, but we share the same belief:
Opinions need to be heard before being judged. People are educated to judge, not to accept judgements.
Apr. 5, 2016
In late March ArkC released V0.3.1, as a tested version with GUI support and redesigned protocols.
Since this version, ArkC developers change their focus to developing a GAE-based server end, with the following design:
Client ===== CDN ====== GAE ====== Website
with control order traffic:
Client ===> DNS servers ====> Supporting VPS translate ======> GAE
In this way there should be little dependency on VPS bandwidth for proxy traffic. We see it as an important enhancement since ArkC.
A new version V0.2.3 was released several days ago. Performance optimized, CDN support enhanced. Also automatic blacklist is introduced into the server side.
If there is an error saying cannot get time from s2a.time.edu.cn at client side, please go to arkcclient/pyotp/totp.py and change the string to cn.pool.ntp.org.
We are redesigning our connection selecting algorithm. In the next version there may be limited backward compatibility.
We have created an Installer to automatically configure ArkC Client along with its GUI. Get it at our GUI github repo.
For version 0.2.1.
We released ArkC V0.2.1 on Feb. 17, with MEEK stability fixes and easier command line options.
We are considering making press appearance to gain more popularity.
On February 11 we released ArkC V0.2.0.post2, on Github and PyPI.
It comes with the following features:
- Easy deployment with pip
- Fixed bugs with uploading
- Enhanced stability
- Explicit private key sha1 prompt
- User-friendly error prompt
Access it our download page or just type in:
pip3 install arkcclient
pip install arkcserver
ArkC Client and ArkC Server are released to PyPI (pypi.python.org).
Access it via:
pip install –pre arkcserver
pip3 install –pre arkcclient
After a long term of silence we release ArkC V0.2 Beta4, probably the last before stable version V0.2. Reach it at our download page.
- Stability with downloading — previous bugs related to HTTPS are fixed
- No waste connections — counting strategies improved
Thanks to Teba (email@example.com) the HTTPS and downloading issues in V0.1.2 betas have been solved. A new beta / formal release is coming soon.