search

gridhead / sanctuary-zero

A command-line bound implementation of secure synchronous lightweight chatroom with zero logging and total transience built using WebSockets, Fernet Cryptography, Asyncio and Prompt Toolkit
GNU General Public License v3.0
58 stars 34 forks source link

Send messages specifically to a chatroom #12

Open gridhead opened 4 years ago

gridhead commented 4 years ago

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.

adhyay2000 commented 4 years ago

Hi, Can i work on this

gridhead commented 4 years ago

Sure thing. I am assigning this to you.

Feel free to leave a star at the repository if you find it helpful.

adhyay2000 commented 4 years ago

Hi, I am thinking of creating a chatroom specific uri that can be used to communicate, without changing the backbone code much. is it correct. for e.g. if the chatroom is 12345678 then the client first ask the server for chatroom and password and create a new connection to the new uri locahost:port/12345678. please provide suggestions.?

adhyay2000 commented 4 years ago

Hi, I have a doubt. Can we have same username across different chat rooms or the name should be unique entirely? like user "aditya" joining room 12345678 and 87654321 at same time.

adhyay2000 commented 4 years ago

Hi, currently the client is sending a message to server and then server is notifying everyone about it, in notify_mesg. I want to select only those websockets at the server side, which correspond to a particular chatroom(users present in the chatroom using those websocket).