| Summary: | Konversation reconnects and rejoins after the client is /kill'd and /kick'd | ||
|---|---|---|---|
| Product: | [Applications] konversation | Reporter: | Chris Nehren <cnehren> |
| Component: | protocol | Assignee: | Konversation Developers <konversation-devel> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | hein |
| Priority: | NOR | ||
| Version: | 1.5-rc1 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | All | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Chris Nehren
2012-12-03 15:14:23 UTC
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. 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@kde.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |hein@kde.org
>
> --- Comment #1 from Eike Hein <hein@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.
No reason for either, other than simply not having special-cased those cases yet. Shouldn't be too difficult, though; channels already keep the relevant state, and handling kills that way is a matter of parsing and funneling the event into the already-existing codepath for deliberate, non-actionable disconnects. Unless I'm missing something you can probably expect the next release to behave this way. Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone! Hello, I'm no longer in a position to test or reproduce this, sorry. Feel free to close. Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Kill handling has not been implemented. |