Before submitting
Area
apps/desktop
Problem or use case
Whenever I put my laptop to sleep for the night, and I log back in in the morning, there is a spam of "disconnected from T3 Server" that I have to dismiss (and have to swipe to, there is no close button yet 😢)
Proposed solution
Ideally, the app should detect when the PC goes to sleep and idle instead of constantly reconnecting to the internal server
Why this matters
I haven't tested battery impact for this (as my laptop is usually just plugged in), but according to Activity Monitor it's somehow been worse than even Discord (where I am in approx 200 guilds 😅). And to clarify, I haven't even been using the app much in the past 12h (6h of those were sleep and the other 6 were idling)
Smallest useful scope
The desktop app should detect sleep states and pause server reconnections until the system is back on from sleep if it doesn't already
Alternatives considered
Alternative would be to pause reconnections entirely if too many happen in a short period of time, and have the user press a button to reconnect manually / do it when they interact with the app again (via opening a thread or such)
Risks or tradeoffs
No response
Examples or references
No response
Contribution
Before submitting
Area
apps/desktop
Problem or use case
Whenever I put my laptop to sleep for the night, and I log back in in the morning, there is a spam of "disconnected from T3 Server" that I have to dismiss (and have to swipe to, there is no close button yet 😢)
Proposed solution
Ideally, the app should detect when the PC goes to sleep and idle instead of constantly reconnecting to the internal server
Why this matters
I haven't tested battery impact for this (as my laptop is usually just plugged in), but according to Activity Monitor it's somehow been worse than even Discord (where I am in approx 200 guilds 😅). And to clarify, I haven't even been using the app much in the past 12h (6h of those were sleep and the other 6 were idling)
Smallest useful scope
The desktop app should detect sleep states and pause server reconnections until the system is back on from sleep if it doesn't already
Alternatives considered
Alternative would be to pause reconnections entirely if too many happen in a short period of time, and have the user press a button to reconnect manually / do it when they interact with the app again (via opening a thread or such)
Risks or tradeoffs
No response
Examples or references
No response
Contribution