Weave messaging application intro underdevelopment

Messaging Application:(underDevelopment)

END-TO-END-ENCRYPTION
As responsibility of a developer and privacy of users, all data transfer between users should be e2e encrypted using Public and Private key pairs.
Public key files are stored on the users encryption table while private keys are only sent once at login. Users could fetch the public key associated with the user they want to send messages to. Authenticated users can get their private keys at login only once and rotated at every login. As a good practice, one should check timestamp on public key of user before sending a new message to get the latest user public key.

TLDR;
This explains how you as the developer can test the. All these sockets are jwt protected. Make sure you're logged in the system and the JWT is not expired.

Chat Basics

These scenarios apply for all types of messages i.e (Text, Files, Voice Notes, Visual Media). Non-Text based messages are first stored on a storage system such as S3, FireStore, Cloudinary and the public media link is sent as the message. The chat system will store that media for 30 days only.

There are 3 presence phases in this. Each for when a different user presence is set i.e ONLINE, AWAY, OFFLINE. And 2 main message states i.e DELIVERED (✓D), READ (✓R).

By default, every message that is sent to any USER or GROUP it is marked with the SENT (✓).

1) There will be a date value in UNIX Timestamp on user presence data for when the data was set.
2) ONLINE presence is stored in REDIS for 1 Hour and updates automatically at every activity
performed.
3) If the user disconnects the socket session, the presence value is updated to AWAY for 72 Hour and
date can be used as last seen.
4) If the system returns null in presence data, that means the user is OFFLINE for longer than the
system can hold record of.

ONLINE
1) Means the user is present in the app and when a message is received a DELIVERED action is
performed.
2) When the user is in a chat room, a READ action is performed on that message.
If the READ action is ignored, the other user/s will not know the message is seen.

AWAY
1) Means the app is in background or killed, the recipient is fired a push notification to his FCM and a
DELIVERED action is performed to notify other user/s about the message state.

OFFLINE
1) Mean the network connection is down, messages are fired to the FCM and collected on a temporary
30 day storage.
2) When network connection is restored, steps from AWAY are performed and message store is
cleared.

GROUP MESSAGES
1) Group messages are assigned to all users in group (you can check the message interface) but does
contain a from and a gid
2) Messages are looped, signed and sent to all topics(users) in the group so they all are notified
Info messages from the system are fired when new members/admins are added, members/admins
are removed, any user leaves or group details are updated