-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pick random vpn server #9
Comments
I feel like pure random is of little use. You'd probably want to connect by default to a small set of servers; perhaps according to some feature (the closest, or less loaded, by country, netflix...). This information is now present thanks to #4 and related to #7 . For this reason, I opened #11. |
What you explain sure has great uses too, that it connects to a "random" server close to you etc.. But trust me sometimes people would like random IP just like with tor browser :) if you have a small set of servers you use, combined with the browser you use, it makes it really easy to identify you, and kinda defeats the purpose of a VPN in some cases. I would personally use a less loaded function a lot in some cases :-) |
Sounds reasonable. Would you care to do the change and submit a merge request? |
I will have a look at it :-) |
An alternative could be to introduce a new command: "pick". By default it would do what you suggest; then, leveraging the information we get in the infos command, it could do much more. Like picking a Netflix server for example or one that has a low load... |
Any update for this feature? |
I just pushed a change to the command start. |
Thank you very much. :D |
Would be nice with a command to connect to a random server.
Example: "nordvpn -r" for truly random server, and "nordvpn -r us" for a random server in the US. ofc you could add --random too :-)
The text was updated successfully, but these errors were encountered: