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
My reason for using this software is to be able to use IRC in situation with intermittent network connectivity, i.e., mobile, trains, etc.
When there is shaky connectivity, the web interface shows a red bar at the top (which is good).
However, it asks me to reconnect (instead of retrying like.e.g, Gmail does) (which is slightly cumbersome), and then asks me to log in again (which is a real hassle), and shows a loading progress bar covering the entire screen (which makes it impossible to even look at the previous content).
I would love to see this be optimized more for semi-online/offline use cases, since I could imagine that an IRC web client is used by more people "on the road" than just me.
The text was updated successfully, but these errors were encountered:
That's a really complicated problem here, that couldn't simply be solved, because it's closely tied to how current Quassel protocol works, which isn't really mobile/web friendly.
When connection is lost for any reason, we are forced to start the connection process again from the beginning.
The current reload + login part is cumbersome I agree, and this could be improved. I could just try to reconnect indefinitely without the need to refresh the page.
My reason for using this software is to be able to use IRC in situation with intermittent network connectivity, i.e., mobile, trains, etc.
When there is shaky connectivity, the web interface shows a red bar at the top (which is good).
However, it asks me to reconnect (instead of retrying like.e.g, Gmail does) (which is slightly cumbersome), and then asks me to log in again (which is a real hassle), and shows a loading progress bar covering the entire screen (which makes it impossible to even look at the previous content).
I would love to see this be optimized more for semi-online/offline use cases, since I could imagine that an IRC web client is used by more people "on the road" than just me.
The text was updated successfully, but these errors were encountered: