In settings I have granitefone, but I won't able to connect to it and it randomly choice .land, but nonetheless in "Current Server" it's still showing up granitefone.
doAutoConnect server= "https://poop.granitefone.me"
Post "http://127.0.0.1:18031\": dial tcp 127.0.0.1:18031: connect: connection refused"
Successfully connected to random server: "https://lite.hush.land" !!!
In settings I have granitefone, but I won't able to connect to it and it randomly choice .land, but nonetheless in "Current Server" it's still showing up granitefone.
```
doAutoConnect server= "https://poop.granitefone.me"
Post "http://127.0.0.1:18031\": dial tcp 127.0.0.1:18031: connect: connection refused"
Successfully connected to random server: "https://lite.hush.land" !!!
```
![image](/attachments/8da23e19-d84f-49cd-982f-62e677a9a52e)
@onryo so this could be either a "bug" or a "feature". Currently it shows you your "currently configured server" but does not show you what server you are on if that server is down. I agree this is confusing. I suggest we change "Current Server" to "Configured server" and keep the same logic of showing what is listed in the config. Then we should add a new line which says "Connected Server" which shows the server we are currently connected to, which will be different than "Configured server" if the configured server is down. If the configured server is up, then both lines will be the same. This will also help in debugging things for users, since we will be able to see which server they have in their config file without them having to find their config file and tell us.
@onryo so this could be either a "bug" or a "feature". Currently it shows you your "currently configured server" but does not show you what server you are on if that server is down. I agree this is confusing. I suggest we change "Current Server" to "Configured server" and keep the same logic of showing what is listed in the config. Then we should add a new line which says "Connected Server" which shows the server we are currently connected to, which will be different than "Configured server" if the configured server is down. If the configured server is up, then both lines will be the same. This will also help in debugging things for users, since we will be able to see which server they have in their config file without them having to find their config file and tell us.
I thought "Current Server" was a "Connected Server", that we could use for debugging already, otherwise why do we need to display it if it is already displayed and configured in Settings by a user?
I thought "Current Server" was a "Connected Server", that we could use for debugging already, otherwise why do we need to display it if it is already displayed and configured in Settings by a user?
@onryo you can go read the code to see how it works. My guess is that it only shows the configured server, which is often the same as the connected server, but not when the configured server is down. I think showing both values, as described above, will be easier to figure out problems for users, which often have no idea how to find or look in files to tell us what is configured.
The reason to show it in this screen is because users can send us a single screenshot of this "about" tab and all the debug info we need would be there, which is not mixed with potential metadata we don't want to see in the Settings.
@onryo you can go read the code to see how it works. My guess is that it only shows the configured server, which is often the same as the connected server, but not when the configured server is down. I think showing both values, as described above, will be easier to figure out problems for users, which often have no idea how to find or look in files to tell us what is configured.
The reason to show it in this screen is because users can send us a single screenshot of this "about" tab and all the debug info we need would be there, which is not mixed with potential metadata we don't want to see in the Settings.
One thing to add is that even if `stickyServer` is set to `true` in "Information about Hush" it displays always "False".
![image](/attachments/42c0da5a-62a8-44cb-b66f-ef8268e0eb73)
From `.config/Hush/SilentDragonLite.conf`:
```
[connection]
server=https://lite.hush.land
[options]
...
stickyServer=true
```
In settings I have granitefone, but I won't able to connect to it and it randomly choice .land, but nonetheless in "Current Server" it's still showing up granitefone.
@onryo so this could be either a "bug" or a "feature". Currently it shows you your "currently configured server" but does not show you what server you are on if that server is down. I agree this is confusing. I suggest we change "Current Server" to "Configured server" and keep the same logic of showing what is listed in the config. Then we should add a new line which says "Connected Server" which shows the server we are currently connected to, which will be different than "Configured server" if the configured server is down. If the configured server is up, then both lines will be the same. This will also help in debugging things for users, since we will be able to see which server they have in their config file without them having to find their config file and tell us.
I thought "Current Server" was a "Connected Server", that we could use for debugging already, otherwise why do we need to display it if it is already displayed and configured in Settings by a user?
@onryo you can go read the code to see how it works. My guess is that it only shows the configured server, which is often the same as the connected server, but not when the configured server is down. I think showing both values, as described above, will be easier to figure out problems for users, which often have no idea how to find or look in files to tell us what is configured.
The reason to show it in this screen is because users can send us a single screenshot of this "about" tab and all the debug info we need would be there, which is not mixed with potential metadata we don't want to see in the Settings.
One thing to add is that even if
stickyServer
is set totrue
in "Information about Hush" it displays always "False".From
.config/Hush/SilentDragonLite.conf
:It was moved to #118, closing.