Skip to content
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

[Feature request] Multihop selects different countries for entry and exit #7103

Open
8 of 10 tasks
acrostich opened this issue Oct 30, 2024 · 0 comments
Open
8 of 10 tasks
Labels
feature request For issues asking for new features

Comments

@acrostich
Copy link

I have checked if others have suggested this already

  • I have checked this issue tracker to see if others have reported similar issues.

Feature description

When using a (large) list of multiple countries for both entry and exit locations, the client often selects the same country for both entry and exit, which defeats some reasons to use the multihop features. Choose different countries for entry and exit locations when several are included in the list used for both.

One way to achieve this would be to (randomly) choose the entry point server then (randomly) choose the exit point in a subset of the list without the servers in the country choosen for the entry point.

Alternative solutions

The current workaround is to create different non-overlapping lists for entry and exit points, but this restriction the choice and is further complicated when one wants to use DAITA as one will also have to track when new servers/countries support this feature.

Type of feature

  • Better privacy/anonymity
  • Better at circumventing censorship
  • Easier to use
  • Other

Operating System

  • Android
  • iOS
  • Windows
  • macOS
  • Linux
@acrostich acrostich added the feature request For issues asking for new features label Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request For issues asking for new features
Projects
None yet
Development

No branches or pull requests

1 participant