An invalid websockets URI must be detected correctly and an elegant exit must be made.

Description

As written, a terminal is cleared using os.system("clear"); however, a Windows' clear command does not use clear, instead, it uses cls. Therefore, I would suggest we check the OS before using clearing command.

Screenshot

Make sure that you use PyInstaller and that it is compliant to Python 3.8 and above.

If I am a user and I wish to know the list of folks currently connected to the chatroom then I should have a convenient command called /list to get the list of everyone connected at the moment.

Fernet is a symmetric-key cryptography so it has its own set of vulnerabilities. How can we make sure that the end-to-end encryption scenario is strengthened all while not making it as complicated as public-key cryptography standard?

Use PyInstaller to generate an EXE file for the client application. That file should have all the constituting dependencies packaged inside it.

Make changes to the code to make it compatible to Windows 10

Base64 does add a bit of redundancy due to padding but it is a much safer and robust way to transfer messages over the network.

Make sure that you use PyInstaller and that it is compliant to Python 3.8 and above.

Which means deadbeef and DEADBEEF are same. This is not supposed to happen.

In the spirit of getting more contributors for the project, the above documents would be appreciated.

Reserved calls include exit, stop, purr, kick etc.

It usually picks the time when the response was asked and gets refreshed only when the message is sent and a new input call is triggered. The usual behaviour of it should be for the prompt to go on changing with respect to time.

Use PyInstaller to generate an EXE file for the server application. That file should have all the constituting dependencies packaged inside it.

The legacy method checks for messages at the client-side and outputs it only if it is subjected to the chatroom that the user has joined. This would lead to network usages even when there is no one sending anything in the chatroom.

The arrow character is not supported in many of the fontfaces so it should be replaced with angular brace.

Make changes to the code to make it compatible to Windows 10

This looks bad. We need to disallow blank names using space check.

It should not head towards the left side where the time and username are displayed when wrapping. Instead, the wrap should be indented to push it forward by at least 22 characters.

@t0xic0der Could we add lint support so that we can have a style guide in place for the project? As the contributors increasing, this will help maintain the decorum of the code.

Seems like a valid feature to have

PR (#43)

It has come to my attention that the code is missing some updated parts; for example:

1. https://github.com/t0xic0der/sanctuary-zero/blob/master/cnew.py#L54 - It is missing prompt_continuation
2. https://github.com/t0xic0der/sanctuary-zero/blob/master/main.py#L35-L48 - duplicate function

@t0xic0der Would you like me to create a PR to patch this?

Check the presence of the username in the chatroom. If they exist, disallow joining. Let them join otherwise.

SIGABRT breaks the connection from the server without trace. Make it act just as if it would with SIGINT (Or simply catch SIGABRT and ignore it)

It should not head towards the left side where the time and username are displayed when wrapping. Instead, the wrap should be indented to push it forward by at least 22 characters.

Since the chatroom generated on new user login are generated at random. there may occur a clash, In such an event two users may land up in the same chatroom without explicitly joining. To create such a condition try replacing the function randgene in cnew.py to give a constant chatroom ID. Possible solution can be generating the chatroom ID from server side. Please correct, if I am wrong.

Check with the server and disallow chatroom creation if a chatroom with the same name already exists.