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

Improve city selection #3

Open
1 of 3 tasks
ericharmeling opened this issue Mar 12, 2020 · 2 comments · Fixed by #8
Open
1 of 3 tasks

Improve city selection #3

ericharmeling opened this issue Mar 12, 2020 · 2 comments · Fixed by #8
Assignees

Comments

@ericharmeling
Copy link
Contributor

ericharmeling commented Mar 12, 2020

We should update the server logic to use "New York" when the client is in an unsupported city. The server should alert the user that their city is not yet supported, and that they could experience much higher latencies as a result.

  • (Quick fix) Set city to "New York" for all requests coming from unsupported cities.
  • Add region selection.
  • Allow any city.
@ericharmeling ericharmeling self-assigned this Mar 12, 2020
@irfansharif
Copy link

Copying over my comment from slack: it would be cool to let the user just pick where their requests are routed through, so they can experience the varying degrees of painful latencies.

@ericharmeling ericharmeling changed the title Use "New York" when in an unsupported city. Improve city selection Apr 6, 2020
@ericharmeling ericharmeling reopened this Jul 16, 2020
@ericharmeling
Copy link
Contributor Author

#8 does not actually resolve this completely. Reopening for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants