It would be very useful if it was possible to kick a client from a bouncer. Inevitably, clients that need kicking appear, whether ghost clients or otherwise, and it would be nice to be able to kick them off.
It would be very useful if it was possible to kick a client from a bouncer. Inevitably, clients that need kicking appear, whether ghost clients or otherwise, and it would be nice to be able to kick them off.
## <bountysource-plugin>
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/23707822-add-the-ability-to-kick-clients-from-a-bouncer?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).
</bountysource-plugin>
<!-- github-sync-id:93072341 -->
There are some distinctly broken clients, a couple relays come to mind, where forcing a reconnect is the most effective option for getting them to work.
That's the main usecase that I can think of.
There are some distinctly broken clients, a couple relays come to mind, where forcing a reconnect is the most effective option for getting them to work.
That's the main usecase that I can think of.
<!-- github-comment-id:118734431 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
It would be very useful if it was possible to kick a client from a bouncer. Inevitably, clients that need kicking appear, whether ghost clients or otherwise, and it would be nice to be able to kick them off.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Usually, clients autoreconnect to server if kicked. So this wouldn't help much.
There are some distinctly broken clients, a couple relays come to mind, where forcing a reconnect is the most effective option for getting them to work.
That's the main usecase that I can think of.