polyphony-chat / polyphony Goto Github PK

In crate::auth::auth, we have the register_fosscord and login_fosscord methods. They do almost the exact same thing, which is send a POST request with a json body to an API route, handling any errors that may occur on the way and return an outcome. This code could very easily be put into one method, which would make it re-usable and remove code duplicates :)

The backend needs an implemented auth::fosscord_login() function, which can then be called from the frontend using a tauri command. The function should take in a backend::FosscordBackend and on success, return a String which is just the token received from the server, nothing else.

Once registration and login (#8) have been implemented in the rust backend, we can use the token we get from these functions to create a serenity client, which should do all the heavy lifting of connecting to a websocket etc. for us. The serenity client should be added to the backend::SpacebarBackend.

no need for this to be a protocol level thing, just on the client is fine, but having speakers in a voice call come from different directions may help with overstimulation / recognising speakers

When #9 gets completed, we can focus on getting all the users' Guilds, the channels in those guilds, and the messages in these channels. I think some additional input is needed here, as to what exactly "getting" means, where we cache these things, if we even cache these things, and how the frontend will ultimately get this information.

To offer a better user experience, it should be considered if we should add a feature which allows an initial synchronization of messages from an already existing device to another, so that all the devices of a user would have the same message history. A potential concern here would be the possible loss of Forward Secrecy if a users device is compromised.