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
Some users may want to use Jamtaba within a private network without an external internet connection active. (E.g. "the internet's gone down, let's have a jam on Jamtaba anyway!")
Allow a user to configure Jamtaba for use only with services inside their local network:
(disable whatever this new public chat thing is)
disable the request to get the list of public servers
disable the global map rendering widget
Potentially allow an alternate "servers" list to be published locally, though I can't see that being widely used.
In this configuration, the user should know that network requests will only be made within their own network and no request will be made to an external, third part IP address, even as a host name look up, etc. This is to avoid any such request blocking until it times out.
Note that each type of request should have a separate option but there should also be a global "off" switch.
The text was updated successfully, but these errors were encountered:
Some users may want to use Jamtaba within a private network without an external internet connection active. (E.g. "the internet's gone down, let's have a jam on Jamtaba anyway!")
Sounds like a very very very very rare situation for me. Implement this will change many different places in the code and possibly will be never used.
Honestly, is not something I will spend my programming time . But if you propose a Pull Request I will merge 😄
Some users may want to use Jamtaba within a private network without an external internet connection active. (E.g. "the internet's gone down, let's have a jam on Jamtaba anyway!")
Allow a user to configure Jamtaba for use only with services inside their local network:
Potentially allow an alternate "servers" list to be published locally, though I can't see that being widely used.
In this configuration, the user should know that network requests will only be made within their own network and no request will be made to an external, third part IP address, even as a host name look up, etc. This is to avoid any such request blocking until it times out.
Note that each type of request should have a separate option but there should also be a global "off" switch.
The text was updated successfully, but these errors were encountered: