Refactor the class of chat_client.js into a React component that wraps the chat client functionality, using nested routes for rendering children components (Contacts, chat/conversation).

Conversation messages are overwritten when opening the view.

• Display connected clients ( usernames, uptime, messages sent )
• Display uptime
• Add options for showing chat (?)

Improve styles on:

• Landing page
• Login
• Loader
• Contacts (check how difficult it would be to merge contacts and conversation view, like other desktop apps such as Telegram or WhatsApp)

Due to the fact that signal protocol's library uses window.crypto, will be necessary to migrate the client application to a browser environment; such as electron.

There must be a few lines with the author, (c), license and the package it belongs to.

• Send server username on connection
• Show chat display and options.

• setState(...): Cannot update during an existing state transition
• Each child in an array or iterator should have a unique "key" prop. Check the render method [...]

• Check for correct parameters ( username ), raise error otherwise.
• Emit connection info to all connected clients

Chat initialization process:

1. Client A sends server 'init-chat' message with the id of client B to start a conversation.
2. Server receives 'init-chat' message and forwards the message to client B.
3. Client B accepts the chat by answering the server with 'accept-chat' and client A's id.
4. A and B can now send 'chat-msg' with each other's Ids.

Steps 1-3 handshake serves as a placeholder for future implementations of Signal's protocol sessions.