I saw that they use OpenVPN protocol[1], then I stopped reading other things. Although the encrypted connections can not be decrypted, the OpenVPN protocol is easy to be detected and banned in some highly censored network.
I recommends the shadowsocks protocol[2] which I used in the censored network, which is hard to be detected and decrypted.
At a glance shadowsocks doesn't look like a secure protocol to me, so even if you use shadowsocks to obfuscate the protocol, you still need to tunnel a secure encrypted protocol inside of shadowsocks.
I don't expect most VPN users to need protocol obfuscation, especially since the IPs of the VPN operator are probably well known. If you're serious about that, you either need your own server or take great effort to hide the entry points (like Tor bridges attempt to).
> the OpenVPN protocol is easy to be detected and banned in some highly censored network.
Tunnelbear are one of the few VPN providers that use a thing called obfsproxy to circumvent this kind of censorship. They call it 'Ghostbear'[0] but really it's just an obfsproxy bundling which uses the domain fronting technique.
You can use a ssl tunnel to avoid DPI detection by your censored network or ISP. It will obfuscate your openvpn tunnel with another ssl layer, although you'll take a performance hit.
Packages like STunnel/stunnel might help(available for both windows/linux).
As for PR workflow, it will be hopefully. There's a discussion[1] to replace the Alioth[2] with Pagure[3], which has a similar workflow with Github. Maybe the Pagure is not the final decision, but it will be a modern platform that's easy for contributors.
A community is not about how many people have permission to write the main repository. Linux kernel is the example. Linus is only one who has permission to write the mainline tree.
True. But Linus also doesn't disappear for several months at a time. Not to mention that Linus is not the only decision maker in the project. Greg KH maintains the stable kernels (which is ironically where most people get their kernel from).
I suggest you looking at Wubi input method[1] which is widely used in China for more than 20 years. My first impression of your method is just the same as Wubi.
The reason why Pinyin input method is more popular, I guess, is that Wubi is too hard to learn which need remember a lot of rules.
But quoted from Wikipedia,
> it is true that Wubi is extremely fast when used by an experienced typist.
So Wubi is still very popular among those who need to type a lot of characters.
I spent a few weeks trying to learn Wubizixing about 10 years ago. I found learning the primary 26 component-to-key mappings very easy via staged practise similar to how I learnt touch typing English, i.e. introducing one new component at a time. (The only minor hiccup was because 木 and 目 both have the same sound and tone in Mandarin, I had to remember that completely visually.)
But when I tried learning the secondary components, I began with the digits 一二三四五六七八九十, I just couldn't remember the keyboard mappings because my mind was already mapping them to the top ten keys in sequence, whereas in Wubizixing they're scattered all over the keyboard based on the first stroke in the character. I gave up on learning Wubizixing after that, and instead looked designing at my own input system.
The most difficult design decision with any such input system is which component-to-key mappings to use. Wuhou uses 92 mappings, Wubizixing uses 26 by overloading many more of the keys. Someone learning such a system must be able to easily learn those mappings.
wubi is based on components of a character, which means typing is super fast at the cost of memorizing all the components. wubihua is based on 4 strokes, first 4 and the last one. It's much simpler to use yet not very fast
I recommends the shadowsocks protocol[2] which I used in the censored network, which is hard to be detected and decrypted.
[1] https://protonvpn.com/secure-vpn
[2] https://github.com/shadowsocks