hadeso-0 / babble Goto Github PK

How to approach

1. When creating the account, the user generates a public and private key pair and saves them in local storage.
2. The user then sends the public key to the server alongside his credentials. THE PRIVATE KEY IS NOT SHARED WITH ANYONE
3. The server receives the user's credentials and his public key, generates a certificate out of the public key, and saves the user in the server.
4. Each time user_A wants to chat with user_B, the server sends user_B's certificate to user_A and vice versa. Each user saves the other's certificate in their local storage to be able to encrypt messages and send them.
5. The ENCRYPTED messages are saved in Monge DB.

Ref:

• https://github.com/muke1908/chat-e2ee
• https://github.com/VertikaJain/react-chat-app
• https://github.com/signalapp/libsignal-protocol-javascript
• https://docs.lens.xyz/docs/encrypted-dms [ Web3 Approach ]

Pre-reqs [ Encryption Algorithms ]:

• Diffie-Hellman Key Exchange Algorithm
• Extended Triple Diffie-Hellman (X3DH)
• Double Ratchet Mechanism

Implement the functions to send files in messages.

How to approach

1. When a user adds a file, the UI must store it in some Array<File>.
2. User can add multiple files and edit the File Array via a cross button on the top-right corner of the file thumbnail.
3. When the user clicks send, the client app must upload each file to the cloud storage (Firebase storage in this case), and send a new chat with __type = type of file [ to appropriately render it on the app ] and content = LINK OF THE UPLOADED DOCUMENT.

Todo-

• #2
• #4
• #3

Using WebRTC APIs we can implement Calling features