Note:
Because translations are set to DOM in escaped form, the texts have to be decoded before.

On disconnect, sockets are in no rooms anymore - even before kicking them out manually.
Because of that, removeClient() did cancel in beginning...
But anaway, we have to remove the client from the unique users list - so force it.

This will temporary leave the channel...

TODO:
- Button for temporary leaving custom channels (Leave with param true)
- Flooding protection!
-- Add closure to client socket, which handles counting emits (By SocketHandler)
-- All client event handlers must call counting method of closure
-- Disconnect client on threshold overflow...

Not finished yet...

TODO:
- Button for temporary leaving custom channels (Leave with param true)
- Disallow permanent leaving of self-created channels (and non-custom channels)
- Deletion of self-created channels
- Response messages after leaving/deleting channels

Also added some client side flood protection to reduce delay effect of irc flood protection...

TODO:
- Webclient: Extend gui for channel creation (What is optional when joining?)
- Temporary leaving custom channels (Without DB update)
- Permanent leaving custom channels (With DB update)

- Flooding protection!
-- Add closure to client socket, which handles counting emits (By SocketHandler)
-- All client event handlers must call counting method of closure
-- Disconnect client on threshold overflow...

- New column CreatorUserID for channel table
- Refactored channel join handler: Validate data on beginning, moved sub routines to methods

TODO:
- Check channel limit (server side)
- Translations for server messages
- Webclient: Extend gui for channel creation (What is optional when joining?)
- Temporary leaving custom channels (Without DB update)
- Permanent leaving custom channels (With DB update)

- Flooding protection!
-- Add closure to client socket, which handles counting emits (By SocketHandler)
-- All client event handlers must call counting method of closure
-- Disconnect client on threshold overflow...

TODO:
- More Tests
- Check channel limit (server side)
- Check channel title/password (server side)
- Webclient: Use checks from server, don't check client side...
- Translations for server messages
- Webclient: Extend gui for channel creation (What is optional when joining?)
- Temporary leaving custom channels (Without DB update)
- Permanent leaving custom channels (With DB update)

TODO:

- Tests
- Check channel limit
- Integrate/check channel password
- Temporary leaving custom channels (Without DB update)
- Permanent leaving custom channels (With DB update)
- Webclient
- Translations for server messages

Extended client customization: New classes for message types; Extracting virtual names from bot messages

Default channel first, then galaxy channel, then individual ones...

This has lead to several problems on smaller sites..