Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

auto away when no frontend client is connected #107

Closed
gdamjan opened this issue Feb 25, 2016 · 12 comments
Closed

auto away when no frontend client is connected #107

gdamjan opened this issue Feb 25, 2016 · 12 comments
Labels
Type: Feature Tickets that describe a desired feature or PRs that add them to the project.
Milestone

Comments

@gdamjan
Copy link
Contributor

gdamjan commented Feb 25, 2016

lounge should set the status to 'away' when there's no client connected on the front-side.

@xPaw xPaw added the Type: Feature Tickets that describe a desired feature or PRs that add them to the project. label Feb 25, 2016
@vectr0n
Copy link

vectr0n commented Mar 1, 2016

+1

@MaxLeiter
Copy link
Member

👍 should be a setting imo

@raqbit
Copy link
Contributor

raqbit commented Apr 8, 2016

+∞

@richrd
Copy link
Member

richrd commented Apr 13, 2016

Very neat idea! Would it be possible to also show who is away in the nick list? Would be very useful.
Apparently it could be achieved with this http://ircv3.net/specs/extensions/away-notify-3.1.html

@xPaw
Copy link
Member

xPaw commented Apr 14, 2016

This should be straight forward to implement:

  • on socketio close -> no more clients? -> send away to all connected irc networks
  • on irc connected -> no socketio clients -> send away to connected irc network
  • on socketio opened -> remove away on all irc networks

This might conflict with users' /away, if they do it.

Am I missing anything? What should the away message be?

@dgw
Copy link
Contributor

dgw commented Apr 14, 2016

Something like "Auto away at <timestamp>", is how ZNC does it.

I'm with @MaxLeiter: This should be a setting, as I already have my ZNC do this and often use a desktop client instead of keeping The Lounge open.

@xPaw
Copy link
Member

xPaw commented Apr 14, 2016

Setting is tricky because we don't have client-sends-settings-to-server.

@dgw
Copy link
Contributor

dgw commented Apr 14, 2016

Then maybe that should be a blocker for this being implemented. I'd probably have to discontinue using The Lounge if there was no way to prevent it from setting me as away just because I don't have it open in a browser tab somewhere. And that would be very sad, because I know of no comparable replacement.

@maxpoulin64
Copy link
Member

Maybe it would be time to get a better settings system going so this is no longer an issue. "We'd need a setting but we can't" seems to be something that comes back fairly often. It would be sad to postpone this one given how simple it would be.

I'll try to see if I can make something in the weekend for the settings, both server-side and client-side.

@dgw
Copy link
Contributor

dgw commented Apr 25, 2016

I see @maxpoulin64 has made good on that in #275. 👍

@maxpoulin64
Copy link
Member

Slight comment as one pointed out on IRC: I had made this branch a while ago: https://github.com/thelounge/lounge/tree/patches/auto-away

It's a quick and dirty fix, but it does add the minimum of support some people need. We're still waiting for a better handling of network preferences and all before this goes into a real PR.

@AlMcKinlay AlMcKinlay added this to the 2.3.0 milestone Apr 17, 2017
@AlMcKinlay
Copy link
Member

Alrighty, this should be fixed by #775, in master and should be in the next release (2.3.0).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Feature Tickets that describe a desired feature or PRs that add them to the project.
Projects
None yet
Development

No branches or pull requests

9 participants