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
When tiny tries to connect to a server and fails, it prints an error message in all channel tabs related to the server
Resolving host...
17:02 Connection error: failed to lookup address information: Name or service not known
The problem with this is, that when tiny tries the connection again a minute later and fails again, the same error message is printed once more.
So imagine you leave your computer on over night and at some point the internet connection drops out. When you then come back in the morning to check your channels, you'll have to scroll past ~60 error messages per hour since disconnect.
It would be nice if that error message was either only printed the first time a connection fails, or kept to the server tab, not the channel tabs.
The text was updated successfully, but these errors were encountered:
Thanks for reporting. I think showing the error just once in all tabs, and then showing the follow up errors only in the server tab makes sense.
Showing the error just once in all tabs (including the server tab) is not great because you won't be able to tell if the client is trying to connect, or it tried once and gave up.
When tiny tries to connect to a server and fails, it prints an error message in all channel tabs related to the server
The problem with this is, that when tiny tries the connection again a minute later and fails again, the same error message is printed once more.
So imagine you leave your computer on over night and at some point the internet connection drops out. When you then come back in the morning to check your channels, you'll have to scroll past ~60 error messages per hour since disconnect.
It would be nice if that error message was either only printed the first time a connection fails, or kept to the server tab, not the channel tabs.
The text was updated successfully, but these errors were encountered: