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] local address for server #175

Closed
Efreak opened this issue Feb 21, 2024 · 3 comments
Closed

[Feature Request] local address for server #175

Efreak opened this issue Feb 21, 2024 · 3 comments

Comments

@Efreak
Copy link

Efreak commented Feb 21, 2024

Please add a local address for the server like dsub uses. When available, connect and use the local server; when not available, connect over the internet.

There's several ways to implement this:

  • ping the local server and check if it's correct type of server in some way (detect from HTML?)
  • use SSID (wifi network name) (dsub and other apps use this. Easier than above, more secure than below)
  • just assume the server is correct and try to log in (possibly disallow insecure login if this method is chosen)
@cstby
Copy link

cstby commented Feb 23, 2024

I'll add that this would be incredibly useful for those of us trying to be careful about server bandwidth or home Internet data usage. I would love to set a transcoding policy based on whether Tempo is connected over LAN or WAN.

@CappielloAntonio
Copy link
Owner

CappielloAntonio commented Jun 1, 2024

Hi, I have implemented the addition of the local address to which to connect instead of using the main address. The algorithm is something like this:
If connected to a local address, it continues to use this until it is reachable, after which it switches to the main address.

If connected to the main address, try to connect to the local address after a fixed X amount of time has passed. If the latter can be reached, use the local one, otherwise continue using the main one.

If the main one is also not reachable then I present a warning message about the unreachability of the server.

The check on which type of connection to use is done every time you enter the app, after a pre-established X time.

At the moment I don't think I will implement an option for ad hoc transcoding by type of address used since the transcoding option by type of connection used already exists. I think this type of control is "stronger" than the previous one.

@CappielloAntonio
Copy link
Owner

The functionality still needs to be fully tested before we can release it, but if you prefer you can test it.
I'm closing this issue, but feel free to reopen it or open a new one if you find any problems.

app-notquitemy-debug.zip

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

No branches or pull requests

3 participants