When Konversation disconnects from IRC due to network problems and then reconnects automatically, it connects to the channel before identifying the user. Ideally it should identify and then re-connect. Reproducible: Always Steps to Reproduce: 1. Wait for network to disrupt connection to IRC 2. Wait for Konversation to automatically reconnect Actual Results: Konversation reconnects to a channel before identifying Expected Results: Konversation should take care of identifying the user before re-establishing connections. Fixing this would greatly improve privacy, especially on Freenode.
To fix this use one of the authentication methods offered by Freenode that doesn't suffer this race condition, namely either using "accountname:password" (with the colon, sans the quotation marks) as the server password in the Server List dialog or (and preferably) SASL authentication if you're using a development version of Konversation (see also http://userbase.kde.org/Konversation/Configuring_SASL_authentication). The client has no reliable means to wait for authentication to complete using any of the other authentication protocols, partly because they are not standardized among networks.
(I should add: To make it more discoverable the server password authentication method is also available in the Identities dialog in the development version, as one of the selectable authentication types in the Auto-Identify group box. A screenshot is visible in the SASL configuration guide linked above.)
Thanks. The "account:password" in the server password seems to be a functional work-around.