search

cypherpunkengineering / cypherpunk-vpn-desktop

Cypherpunk Privacy VPN app for Windows / MacOS / Linux
Other
0 stars 0 forks source link

Rename smart DNS setting to CypherPlay(tm) and move it into Basic Settings #44

Closed wiz closed 7 years ago

wiz commented 7 years ago

Of course, if enabled then "Use Cypherpunk DNS" must also be enabled, so I guess we have to prevent disabling that setting when CypherPlay is enabled ?

nikuhodai commented 7 years ago

The problem is not the effort of graying out some other setting, but the fact that this setting can easily break things (same as any DNS override), e.g. suddenly local network servers are no longer accessible by name. There's no indication the user is taking this risk by turning on "CypherPlay".

If we're committed to subjecting the user to this risk, it's more straight-forward to simply say that these settings are implicitly on (i.e. they're not even settings, just sales bullet points), and then we just have an advanced "Use Existing DNS" compatibility setting for users who have problems with the default/recommended behavior.

Also, "CypherPlay" is pretty blatantly about bypassing streaming service geo-blocking, so I guess we're not worrying about legal pressure?

wiz commented 7 years ago

Those are some very good points... so I guess we should implicitly use Cypherpunk DNS by default, and just have a compatibility setting for "Use Existing DNS", which would grey out CypherPlay and Content Filters?

The CypherPlay setting probably shouldn't be enabled by default because it uses a lot of extra server resources, and would break the VPN entirely if the smart dns server backend failed.

In regards to the blatant bypassing of streaming services, yes, we are going to actively advertise and market that we do this - it's going to be our flagship feature and a major selling point, it's what will separate from the rest of the industry, etc.

nikuhodai commented 7 years ago

I think swapping around the settings so they're on unless disabled (for compatibility) makes for a cleaner UX, yes. "If you have problems with your connection, please explore the available compatibility settings", basically.

Are there any other settings we want to consider moving up to basic settings rather than advanced? We haven't thought much about this until now, and some of the stuff hidden in advanced may be reasonably useful enough to warrant being visible by default. (The malware/ad blocking springs to mind.)

nikuhodai commented 7 years ago

Reworked into new main screen instead.