Bug 177960

Summary: on start get away-status from server
Product: [Applications] konversation Reporter: Emil Obermayr <nobs>
Component: generalAssignee: Konversation Bugs <konversation-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: wishlist CC: hein
Priority: NOR    
Version First Reported In: 1.0.1   
Target Milestone: ---   
Platform: openSUSE   
OS: Unspecified   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Emil Obermayr 2008-12-17 05:59:00 UTC 
Version:           1.0.1 (using KDE 3.5.9)
Installed from:    SuSE RPMs

When logging on to a server that activates /away per default konversation is in the wrong state because it assumes /away is off.

This most likely happens with bouncers/proxies.

Solution: get the away-status from the server at startup
Comment 1 Eike Hein 2008-12-18 12:37:03 UTC 
It doesn't work that way. IRC is server-as-authority, i.e. the client reacts to what the server tells it to do. A client is correct to assume that it isn't in away state unless the server tells it that it is after a connection has been established. In the case of a bouncer/proxy, it's the bouncer's job to relay the away state to a connecting client; the client shouldn't have to ask for it. Please file a bug report with the developers of your bouncer/proxy.

To further exemplify the server-as-authority nature of IRC:
- When a user issues a /join command, the client actually only opens a channel in response to being told by the server that it has joined that channel.
- When a user issues a /away <reason> comment, the client actually only switches into the away state in response to being told by the server that it has entered the away state.