Open djasa opened 2 years ago
How about this policy:
Hi Shengyu,
This unfortunately wouldn't work for me. I use (bounced) IRC at work and I often connect from outside via VPN, while sometimes it's perfectly OK for me to work for a while offline (avoiding metered data use and distractions), sometimes I try hotspots (again to save my metered data) that don't offer full connection until I go through the captive portal.
If my reboot (usually once per week or two) is at work, srain would be annoying exactly as today with the proposed policy because it would connect without issues first, but then would come first suspend followed by resume at different location with a different connectivity.
NM has notion of all of these (including metered data, if you want to be extra nifty, skip url preloading when on such a connection…), hopefully exposed at some standardized org.freedesktop.something interface.
Dne čt 1. 9. 2022 8:14 uživatel Shengyu Zhang @.***> napsal:
How about this policy:
- If the connection has been established once, produce a notification for every failure
- If not, only produce a notification for the first failure (but keep reconnecting)
— Reply to this email directly, view it on GitHub https://github.com/SrainApp/srain/issues/376#issuecomment-1233791615, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKXO4W2ANMKECOF6OR4T5TV4BCT5ANCNFSM6AAAAAAQBPVV7M . You are receiving this because you authored the thread.Message ID: @.***>
Okay, I get it. How about notifying for once, until it is successfully connected again?
Srain is not in active development, but I think we can improve this in the next minor release.
Okay, I get it. How about notifying for once, until it is successfully connected again?
Yeah, that would be great from my POV.
Srain is not in active development, but I think we can improve this in the next minor release.
Got it. I tried using srain over last week as my primary IRC client and these new issues are the result. :) Without fixing this one, I couldn't use it long-term. Overall, I like it more than not as it gets most of basic stuff right.
srain produces notification per every
Failed to connect to NETWORK
event. I see two instances of it:Version