You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
changed the title
Use "New York" when in an unsupported city.
Improve city selection
Apr 6, 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.
The text was updated successfully, but these errors were encountered: