[Konversation-devel] [Bug 311086] Konversation reconnects and rejoins after the client is /kill'd and /kick'd

[Chris Nehren]

https://bugs.kde.org/show_bug.cgi?id=311086

--- Comment #2 from Chris Nehren <cnehren at pobox.com> ---
On Mon, Dec 03, 2012 at 16:02:14 +0000 , Eike Hein wrote:
> https://bugs.kde.org/show_bug.cgi?id=311086
> 
> Eike Hein <hein at kde.org> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |hein at kde.org
> 
> --- Comment #1 from Eike Hein <hein at kde.org> ---
> Konversation doesn't auto-rejoin after kicks - intentionally, despite frequent
> user requests, because we agree it only aids trolls and bad operators. Kills
> however are not treated differently from other forms of connection loss.

I think what happened with the rejoin-after-kick is:

1. user joined channel
2. user was kicked from channel
3. user's connection dropped
4. user reconnected, and rejoined

I'd say this is a bug, though admittedly a difficult one to fix. Whether
you want it filed separately or not is up to you.

Why are kills not treated separately? If an oper /kills a user, they
want that user off of their network, and reconnecting will only make
things worse.

-- 
You are receiving this mail because:
You are the assignee for the bug.