Older versions of
Psi jabber client required manual changing status to online to leave auto-offline state. It was very handy for me: I connect to my jabber account from two locations (from home and from office), so after I left one of these locations, auto-offline soon happened, and Psi at that location did not return online until I returned and manually instructed it to re-login.
Unfortunately newer versions of Psi (I guess, starting from commit 4a54500c on
git://git.psi-im.org/psi.git, which was between 0.11 and 0.12 releases), and also
Psi+, behave differently: if user activity is detected on the desktop, auto-offline state is left, and status becomes online again similar to leaving auto-away and auto-xa states.
This change is not good for me, at least in two situations:
- vnc connection to home from office or to office from home I use this fairy often,
- occasional use of my home session by my wife for quick web browsing or similar.
In both these situations, Psi client not at my current location becomes online, which can cause routing incoming messages to wrong location.
I don t state that new behaviour is somehow worse than old behaviour. But for my use cases, I want to get old behaviour back.
I ve done some code reading. I think that point to fix is near the bottom of
PsiAccount::secondsIdle() method, where any auto status is disabled if no timeout condition currently exists. This should be changed so that auto-offline state won t be left if some config key is set.
I will try to implement this change soon (or at least I hope I will try )
P.S.
To make things even better, a check of some external condition could be performed to decide if client should return online from auto-offline or not. Then fancy things could be set up, e.g. return to online at office only if my mobile phone is currently registered in the office wifi network not really required but cool.