Volatile Private Messaging System #155

New issue

Closed

opened 2025-09-14 07:14:42 -04:00 by rainbownapkin · 5 comments

rainbownapkin commented

2025-09-14 07:14:42 -04:00

(Migrated from gitlab.com)

We do not currently have the time to implement the end-to-end encryption necessary for properly storing private messages, so for now they should be volatile a-la cytube/fore.st.

We should create a basic messaging panel with tabs for each user you're actively talking to. Each message should be emitted to the users sockets across ALL connected channels.

Messages must NOT be logged or saved in anyway server-side as end-to-end encryption isn't implemented. The server should relay and forget. Even though this means users won't be able to receive messages when offline, or look at old ones after a refresh.

We do not currently have the time to implement the end-to-end encryption necessary for properly storing private messages, so for now they should be volatile a-la cytube/fore.st. We should create a basic messaging panel with tabs for each user you're actively talking to. Each message should be emitted to the users sockets across ALL connected channels. Messages must *NOT* be logged or saved in anyway server-side as end-to-end encryption isn't implemented. The server should relay and forget. Even though this means users won't be able to receive messages when offline, or look at old ones after a refresh.

rainbownapkin commented

2025-09-14 07:15:39 -04:00

(Migrated from gitlab.com)

added #156 as child task