-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
FR: Improve Mullvad exit-node selection lists on Windows and Android #9421
Comments
We've rolled out UI/UX changes for the CLI and iOS, and further updates to the other clients will be happening before we consider the feature generally available (it's currently in beta). Which platforms are you using? |
My Windows and Android devices are where I'm worried about being able to use exit nodes. |
Hi all, Just wanted to comment that I am still having this issue on the Windows 11 Tailscale client. I have a massive list of all available Mullvad servers in my exit-node list, making it pretty much unusable on Windows. Works perfectly on MacOS, though! |
This change provides minor improvements to the exit node menu when there are location based exit nodes present. It will ensure that non location based exit nodes are displayed at the top of the list, followed by a the best node for a country/city combination, and followed by all location based exit nodes. Updates tailscale/tailscale#9421 Signed-off-by: Charlotte Brandhorst-Satzkorn <charlotte@tailscale.com>
…159) This change provides minor improvements to the exit node menu when there are location based exit nodes present. It will ensure that non location based exit nodes are displayed at the top of the list, followed by a the best node for a country/city combination, and followed by all location based exit nodes. Updates tailscale/tailscale#9421 Signed-off-by: Charlotte Brandhorst-Satzkorn <charlotte@tailscale.com>
Hi - here with an Android update. I've rolled out a small usability improvement to the exit node menu - you can get access to it now on our unstable android release (https://tailscale.com/kb/1083/install-unstable) and this change will also be included in our next stable release. There will be more extensive changes made by the android engineers in the future. |
…159) This change provides minor improvements to the exit node menu when there are location based exit nodes present. It will ensure that non location based exit nodes are displayed at the top of the list, followed by a the best node for a country/city combination, and followed by all location based exit nodes. Updates tailscale/tailscale#9421 Signed-off-by: Charlotte Brandhorst-Satzkorn <charlotte@tailscale.com>
This comment was marked as off-topic.
This comment was marked as off-topic.
Thanks for the update @catzkorn - that's much nicer! Do you have any insight to when the next release may be cut so we can start using it? |
@aw1cks hi! the 1.60 release is currently in open testing in the play store, we are looking to move it to GA soon. (hopefully in the next few days!) |
The Android client menu looks great. Please update the Windows client to also group Mullvad exit notes by country and city. This would save me having to click my mouse a hundred times to find the one that I'm looking for. Otherwise, Tailscale is wonderful and has saved me a ton of time and money! :) |
Updates tailscale/tailscale#9421 Adds a view to highlight Mullvad support when it is not enabled. Signed-off-by: Andrea Gottardo <andrea@gottardo.me>
Updates tailscale/tailscale#9421 Adds a view to highlight Mullvad support when it is not enabled. Signed-off-by: Andrea Gottardo <andrea@gottardo.me>
Updates tailscale/tailscale#9421 Adds a view to highlight Mullvad support when it is not enabled. Signed-off-by: Andrea Gottardo <andrea@gottardo.me>
What are you trying to do?
There's a lot of Mullvad exit nodes, and no stats to help users identify which particular exit node is the best available. (I'm not even going to get into the hell that is the current exit-node selector for Windows and Android. You know it needs work.)
How should we solve this?
In the exit node selector, nodes are probably going to be organized in nested menus by country > city > server list. I propose that at the top of each nested list, you provide a "best available" option that automatically chooses a server by load and latency.
On the country list, it'd pick the best server globally. On the city list, it'd pick the best server in that country. On the server list for a city, it'd pick the best node in that city.
What is the impact of not solving this?
Currently, when I need an exit node, I'm finding the country or city I want and picking at random, hoping that enough others are doing the same that I wind up on a not-overloaded server with a decent ping.
Anything else?
No clue if this is possible, but hey, it'd be nice.
The text was updated successfully, but these errors were encountered: