Ghost nicknames

[iamthemexic...@gmail.com]

I installed a standalone KiwiIRC on my server. Often when a user disconnects and reconnects thir nick remains on the IRC server as a ghost and Kiwi adds 01 to their new nick. I have to restart the KiwiIRC process on my server to clear this caching. Is there a way around this?

[prawnsalad]

Does this always happen with the same user or different people at seemingly random times?

There is an issue where peoples nicks stay connected when they close the browser for some reason that we're looking into, but it doesn't usually happen often. If your an admin on the IRC network or if you could ask an admin, they should be able to /kill the ghost nick.

Darren

[iamthemexic...@gmail.com]

It seems to happen often and with multiple users. I've been running KiwiIRC on my server for a week now and it happens pretty much everyday. The only way to fix it is to kill the kiwi process and restart and the connections clear out. It really seems to be like Kiwi is caching the connections somehow even if the browser is closed. Perhaps some sort of timeout can be implemented or a regular ping from kiwi process to the user's IP and kill their connection if there is no reply from user's browser for sometime? Unfortunately I'm not an admin on the IRC server itself and can't /kill usernames. It would also not be very convienient as the userbase of my chatroom grows.

[mi...@njuh.nl]

I've encountered this for quite a few users too, it doesn't even add 01 for me but just pops up the nickname change box. (This is when it automatically tries to reconnect, even with the conf.ircd_reconnect setting set to false)

I often had the problem you describe here too where Kiwi would keep the connection open when the user closed their browser, as a temporary workaround I've taken out the beforeunload popup in /client/src/views/application.js and added a plugin with the following code:

<script>
window.addEventListener("beforeunload", function(e){
kiwi.components.Network().quit('Closing tab')
}, false);
</script>

This at least solves it for when people gracefully close their tabs. But it seems like it needs some work on server side to check if the client is still there. I'll update if I find a proper solution to this

[iamthemexic...@gmail.com]

I'll try it, big thanks!